S3Drive - CORS setup Backblaze

Hi. Looking for some basic setup help. I setup Backblaze B2 buckets and installed the S3Drive app. I was able to make connections to my buckets and able to upload files. I purchased lifetime ultimate S3 and can no longer connect to my backblaze, i had deleted the original profile that was created when I was testing. I can create and upload files on S3Drive apps but don't see them in my backblaze buckets. I've tried creating new buckets and creating new api's but now I can't get the api's to connect when i try and add a new profile. should my backblaze be connected to my ultimate managed profile? I'm receiving a XMLHttpRequest Error to set up CORS (I didn't do this originally) I tried setting them to: Share everything in this bucket with every origin. Please let me know what I'm doing wrong.

Hi, thank you for supporting us. You only need an Ultimate account for S3Drive to recognize your license, so you can use all of the paid features. I am not sure if you've seen it already, but we've got a specific guide to setting up Backblaze bucket: https://docs.s3drive.app/setup/#create-bucket You'll need to setup CORS on your bucket first in order to use the web client: https://web.s3drive.app/

8:56 AM

Here is the: "Set up CORS" setting. If you have multiple accounts, including managed / ultimate account you obviously need to switch to your "Backblaze" bucket as indicated on screenshots I've just attached.

CORS setting needs to be applies for each new bucket separately... and last time when we've tested Backblaze's: "Share everything in this bucket with every origin" setting it didn't work for us.

Hi @Tom I’ll give it another try. What’s the specific CORS setting I should use?

If you use: "Set up CORS" option, S3Drive will set it up for you, if you would like to set it up yourself please find this post: https://discord.com/channels/1069654792902815845/1136595431934132265/1136703365842206780 (edited)

Tom changed the channel name: CORS setup Backblaze 12/29/2023 4:05 PM

Tom

Here is the: "Set up CORS" setting. If you have multiple accounts, including managed / ultimate account you obviously need to switch to your "Backblaze" bucket as indicated on screenshots I've just attached.

@Tom I think I got it sorted out. Thanks for the prompt response!

1

Hi! Just following up on this, same issue. (But it's on the Web App) What is the configuration needed for my bucket? (CORS)

We use these settings:

 <CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <CORSRule>
        <ID>S3Drive</ID>
        <AllowedOrigin>https://web.s3drive.app</AllowedOrigin>
        <AllowedMethod>GET</AllowedMethod>
        <AllowedMethod>HEAD</AllowedMethod>
        <AllowedMethod>POST</AllowedMethod>
        <AllowedMethod>PUT</AllowedMethod>
        <AllowedMethod>DELETE</AllowedMethod>
        <MaxAgeSeconds>3600</MaxAgeSeconds>
        <ExposeHeader>etag</ExposeHeader>
        <ExposeHeader>x-amz-meta-x-amz-key</ExposeHeader>
        <ExposeHeader>x-amz-meta-x-amz-iv</ExposeHeader>
        <ExposeHeader>x-amz-meta-x-amz-cek-alg</ExposeHeader>
        <ExposeHeader>x-amz-meta-x-amz-wrap-alg</ExposeHeader>
        <ExposeHeader>x-amz-meta-x-amz-key-v2</ExposeHeader>
        <ExposeHeader>x-amz-meta-x-amz-tag-len</ExposeHeader>
        <ExposeHeader>x-amz-meta-x-amz-unencrypted-content-length</ExposeHeader>
        <ExposeHeader>x-amz-version-id</ExposeHeader>
        
        <ExposeHeader>x-amz-meta-key</ExposeHeader>
        <ExposeHeader>x-amz-meta-iv</ExposeHeader>
        <ExposeHeader>x-amz-meta-chunk</ExposeHeader>
        <ExposeHeader>x-amz-meta-cek-alg</ExposeHeader>       
        
        <ExposeHeader>x-amz-meta-s3drive</ExposeHeader>  
        
        <ExposeHeader>x-amz-meta-mtime</ExposeHeader>
          
        <AllowedHeader>*</AllowedHeader>
    </CORSRule>
</CORSConfiguration>

but app in principle should configure it for you. If "Set up CORS" button doesn't work for you on Web, then try configuring bucket on desktop/mobile and click: Set up CORS from the Profile settings. Our experience was that Backblaze CORS settings configured using their website haven't worked, I am not sure if they have fixed that already.

Will try that, thanks Tom!